The application must utilize FIPS-validated cryptographic modules when signing application components.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-222570	APSC-DV-002020	SV-222570r508029_rule		Medium

Description
Applications that distribute components of the application must sign the components to provide an identity assurance to consumers of the application component. Components can include application messages or application code. Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to validate the author of application components. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance the modules have been tested and validated. If the application resides on a National Security System (NSS) it must not use algorithms weaker than SHA-384.

Description

Applications that distribute components of the application must sign the components to provide an identity assurance to consumers of the application component. Components can include application messages or application code. Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to validate the author of application components. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance the modules have been tested and validated. If the application resides on a National Security System (NSS) it must not use algorithms weaker than SHA-384.

STIG	Date
Application Security and Development Security Technical Implementation Guide	2020-09-30

Details

Check Text ( C-24240r493618_chk )
Review the application documentation and interview the application administrator to identify the cryptographic modules used by the application. Review the application components and application requirements. Interview application developers and application admins to determine if code signing is performed on distributable application components, files or packages. For example, a developer may sign application code components or an admin may sign application files or packages in order to provide application consumers with integrity assurances. If signing has been identified in the application security plan as not being required and if a documented acceptance of risk is provided, this is not a finding. Have the application admin or the developer demonstrate how the signing algorithms are used and how signing of components including files, code and packages is performed. While SHA1 is currently FIPS-140-2 approved, due to known vulnerabilities with this algorithm, DoD PKI policy prohibits the use of SHA1 as of December 2016. See DoD CIO Memo Subject: Revised Schedule to Update DoD Public Key Infrastructure Certificates to Secure Hash Algorithm-256. If the application signing process does not use FIPS validated cryptographic modules, or if the signing process includes SHA1 or MD5 hashing algorithms, this is a finding.

Check Text ( C-24240r493618_chk )

Review the application documentation and interview the application administrator to identify the cryptographic modules used by the application.

Review the application components and application requirements. Interview application developers and application admins to determine if code signing is performed on distributable application components, files or packages.

For example, a developer may sign application code components or an admin may sign application files or packages in order to provide application consumers with integrity assurances.

If signing has been identified in the application security plan as not being required and if a documented acceptance of risk is provided, this is not a finding.

Have the application admin or the developer demonstrate how the signing algorithms are used and how signing of components including files, code and packages is performed.

While SHA1 is currently FIPS-140-2 approved, due to known vulnerabilities with this algorithm, DoD PKI policy prohibits the use of SHA1 as of December 2016. See DoD CIO Memo Subject: Revised Schedule to Update DoD Public Key Infrastructure Certificates to Secure Hash Algorithm-256.

If the application signing process does not use FIPS validated cryptographic modules, or if the signing process includes SHA1 or MD5 hashing algorithms, this is a finding.

Fix Text (F-24229r493619_fix)
Utilize FIPS-validated algorithms when signing application components.